TPX-IoT-Flow 1.8.X

1.8.1a

MAJOR BUGS RESOLVED

JIRA Ticket	Description
TXIF-3752	TPX-LE Processor could cause issue on uplink if debug mode wasn't used.

1.8.1

MAJOR BUGS RESOLVED

JIRA Ticket	Description
TXIF-3613	Kafka flow should not be stopped when Driver-Engine return an unexpected format.
TXIF-3618	Downlinks that should be encoded and published by the AS are rejected.
TXIF-3623	TPW user only - Unable to encode payload using custom drivers forced in the Flow.
TXIF-3628	TPW user only - Unable to encode payload using custom drivers forced in the Flow with Generic Device Profiles.
TXIF-3639	Tpx-API - Encode downlink doesn't work on a custom driver from UI.
TXIF-3662	HTTP Connector - Destination URL extended up to 512 characters.

1.8.0a

MAJOR BUGS RESOLVED

JIRA Ticket	Description
TXIF-3612	ReconnectionStrategy - Wrong enumeration type.

1.8.0

Release Goals

This major release is mainly a technical upgrade.
The framework and SDK have been upgraded, and the application now uses Java 17.
We have worked to fix all critical and high CVEs, improved internal mechanisms, reworked the code for optimization, and enhanced monitoring.

A new message counter named "Lost uplinks" has been introduced to track uplinks intentionally skipped due to a filter or an exclusion rule.

---

Processors

Chirpstack V4 format

In the Output Stream Processors panel of your connection, you can now automatically transform Actility uplinks into the Chirpstack V4 uplink format.

Example of a generated Chirpstack V4 uplink:

{
  "devEUI": "JOEkclwSEEA=",
  "fPort": 85,
  "deviceName": "Milesight - AM103",
  "fCnt": 11527,
  "adr": true,
  "applicationName": "msight:am100-series:1",
  "rxInfo": [
    {
      "rssi": -50,
      "loRaSNR": 9.5,
      "rfChain": 1,
      "gatewayID": "EAAxsw==",
      "time": "2025-08-14T08:38:40.821Z"
    },
    {
      "rssi": -105,
      "loRaSNR": 8.75,
      "rfChain": 0,
      "gatewayID": "EAAJqQ=="
    },
    {
      "rssi": -72,
      "loRaSNR": 8.25,
      "rfChain": 0,
      "gatewayID": "EAAANQ=="
    }
  ],
  "data": "AXUmA2fuAARodQd9jwI=",
  "objectJSON": "{\"battery\":38,\"temperature\":23.8,\"humidity\":58.5,\"co2\":655}",
  "txInfo": {
    "frequency": 867700000,
    "modulation": "LORA",
    "loRaModulationInfo": {
      "spreadingFactor": 7
    }
  }
}

Connectors

Disable decoding of uplinks

In the Advanced settings panel of each connection, you can now choose to disable automatic payload decoding.
By default, decoding remains enabled.

---

New Features Released

JIRA Ticket	Description
TXIF-2293	Major framework and SDK upgrade.
TXIF-2993	Migration to Java 17.
TXIF-3389	Fix for all critical and major CVEs.
TXIF-2294	New processor – Chirpstack V4.
TXIF-3084	Azure Event-Hub Connector – Support for TLS 1.3.
TXIF-2798	Cumulocity Connector – Support for custom CA certificates.
TXIF-2924	All Connectors – DriverEnabled option to disable uplink decoding (enabled by default).

---

Major Bugs Resolved

JIRA Ticket	Description
TXIF-3104	Azure IoT-Central Connector – Support for multiple hubs.
TXIF-3364	Fixed downlink failure counter issue when a downlink failed via REST API.
TXIF-3239	Modbus connectors – Dashes in DeviceEUI are now automatically removed.
TXIF-2635	Thingworx connectors – Internal cache synchronized when a Thing is removed on the Thingworx side.